- Introduced Testnet4 configuration in  with a new Electrum server URL.
- Updated  to include Testnet4 for Bitcoin networks.
- Added Testnet4 constant in  for better network identification.
- Adjusted test cases in  for improved readability.
- Updated Hardhat configuration files to streamline deployment processes and handle potential errors during verification.

…ort.json file

- Removed a defunct Thesis Electrum URL from the expected peers in .
- Deleted the  file as it is no longer needed, streamlining the project structure.

…waffle

…ict deps)

…ackage.json and yarn.lock for ECDSA and random-beacon

…abi version in ECDSA and random-beacon

…andom-beacon

… for new network

…g in deployment scripts

…rove setup

…etup

…flows

…rkflows

… script for improved environment isolation

… workflows

…fig file and enhancing environment handling

…ent for mainnet compatibility

… replace deprecated IP address

…n test networks to improve reliability

…ailable data for various networks

…ervers and adding error handling for integration tests

…to skip outdated public endpoints

…tOwner function with governance checks and error handling

… addresses, transaction hashes, and gas usage metrics

withdrawRewards resolves the beneficiary via _currentAuthorizationSource().
Replace stale NOT MIGRATED / TokenStaking-only commentary with accurate
routing, delegated-setup divergence, TIP-092/100 reward halt context, and
future reactivation semantics.

Made-with: Cursor

…s and update Hardhat configuration for plugin compatibility

…resses, transaction hashes, and gas metrics for multiple contracts

…specific group parameters for improved deployment on testnets

…for enhanced group parameter configuration

…ain for reliable retargeting

…aintainer for handling preflight errors gracefully

…improved transaction confirmation reliability

…ficulty maintainer's pre-retarget validation for better handling of minimum-difficulty blocks

…resses, transaction hashes, and gas metrics for multiple contracts

…ialization for improved readability

…ic block sequence and simplifying timeout handling for better reliability

…n to ensure proper behavior when multiple members submit claims

…g in DKG execution

The rebase used -X theirs to resolve conflicts, which silently dropped two
items that existed in both main and the pre-rebase branch:

- .github/workflows/contracts-ecdsa.yml: --compile-force-framework hardhat
  flag for slither
- solidity/ecdsa/package.json: get-func-name ^2.0.2 resolution

…ution

Mirrors recent dependabot bumps on main:
- handlebars 4.7.7 -> 4.7.9 (random-beacon threshold-network#3916, prototype pollution fix)
- immutable 4.0.0-rc.15 -> 4.3.8 (random-beacon threshold-network#3879)

Added as Yarn 4 resolutions in both random-beacon and ecdsa to keep parity
across solidity workspaces and avoid post-merge dependabot churn.

Duplicate Allowlist identifier in test imports broke both lint
(no-redeclare) and tsc (TS2300) builds on CI.

getProofInfo assumed every proof header carries the relay epoch difficulty,
so with txProofDifficultyFactor=1 it assembled single-header proofs. On
testnet4 (BIP94), sweeps mined in minimum-difficulty blocks produced proofs
containing only a DIFF1 header, which the Bridge rejects with "Not at
current or previous difficulty".

Mirror the Bridge's BitcoinTx logic instead: skip leading DIFF1 headers
when both relay epochs are above minimum, bind the requested difficulty to
the first decisive header matching the relay's current or previous epoch
difficulty, and accumulate headers until their total observed difficulty
covers requestedDifficulty * txProofDifficultyFactor.